ci: workflow_dispatch release — no more local tag pushes#4
Merged
Conversation
Releasing previously required a local tag push, which the session permission layer blocked twice this week, falling back to manual terminal work. The workflow now supports dispatch with a version input: verifies the version against package.json, runs the full check suite, publishes to npm, and creates the tag AND the GitHub Release with notes extracted from that version's CHANGELOG section (bilingual notes preserved — this also automates what was a manual release-create step for 0.1.0). Tag-push releases still work as a fallback and now get the same auto-created Release. permissions.contents: write is required for the Release step.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why / 왜
릴리스마다 로컬에서 태그를 만들어 푸시해야 했고, 이번 주에 그 푸시가 세션 권한 레이어에 두 번 막혀 수동 터미널 작업이 됐습니다. 태그 푸시 자체를 없애면 마찰 지점이 근본적으로 사라집니다.
What / 무엇
한 줄이면: package.json 버전 일치 검증 → typecheck/test/build → npm publish → 태그 생성 + GitHub Release 생성 (해당 버전의 CHANGELOG 섹션을 릴리스 노트로 추출 — 이중언어 수기 CHANGELOG 컨벤션 유지, 0.1.0 때 수동으로 한 release 생성도 자동화).
permissions.contents: write— Release/태그 생성에 필요 (기존 read)New release flow / 새 릴리스 플로우
gh workflow run publish.yml디스패치 → 나머지 전부 CI